docs(board): retroactive batch hygiene for #510 / #511 / #512 / #513#516
Conversation
PR #510 merged 2026-06-16 16:36 UTC (merge commit 0e6452c) on main — +125/-0 additive seam falsifier in crates/surreal_container/tests/ scheduler_seam.rs (first integration-test file in surreal_container). Five kill-condition-first tests pin the IN-direction of the surreal↔ kanban↔scheduler wiring (SurrealMailboxView → NextPhaseScheduler:: on_version → KanbanMove) against the real view (not FakeView): 1. full_rubicon_arc_lowers_to_legal_successors 2. absorbing_columns_schedule_no_move 3. libet_anchor_only_on_sigma_commit_crossing 4. lowering_is_deterministic 5. exec_target_rides_onto_the_move Out of scope (deferred, explicit in PR body): the OUT-direction = planner-emit KanbanMove (CognitiveCycle sequencer + §9 LOCKED from #496). D-MBX-A6-P3 remains the next unblock for closing the loop. This PR proves the downstream half; upstream still hand-rolled. Retroactive board update (merge landed before the same-commit hygiene rule could fire). Two files: PR_ARC_INVENTORY (prepend), LATEST_STATE (dated bullet + table row). https://claude.ai/code/session_01Xzyc27Nx3f8WC5KzwfWfjx
PR #511 merged 2026-06-16 19:01 UTC (merge commit c3dddfc) on main — +886/-0 additive substrate calibration in perturbation-sim: examples/calibrate.rs (ICC/Spearman/Pearson/Cronbach α battery against perturbation-sim as ground truth), src/columns.rs (calibrated SoaMemberSpec, spec only), src/hhtl.rs, examples/hhtl_grid.rs, CLAM_CHAODA_FRAMING.md. Headline locks: - 5 contingency factors certify by VALUE at 2-bit linear (ICC ≥ 0.96) — existing palette/turbovec tenants suffice; §10 "statistics survive the encoding" CONFIRMED. - α preserved within Δ ≤ 0.02 at ≥4-bit; read ≥6-bit for orthogonality. - inertia_buffer is the one genuinely additive member — orthogonal to topology per #509 (Spearman(λ₂, buffer) ≈ 0). Spec only; promotion gated by §0 anti-invention guardrail. - d_lambda2's ICC=0 was a variance-guard underflow at ~1e-7 magnitude; two prior guesses (heavy-tail / near-constant) retracted on the run. - Significance per Jirak n^(p/2−1) (I-NOISE-FLOOR-JIRAK). - Does NOT touch the operator-locked canonical_node. Files updated this commit: - PR_ARC_INVENTORY.md PREPEND #511 entry - LATEST_STATE.md dated bullet + Recently-Shipped row - AGENT_LOG.md PREPEND session entry covering both odoo-rs SEED (cross-repo, commit ebfb2c3 on AdaWorldAPI/odoo-rs main) AND this #511 board hygiene. Retroactive cleanup (merge landed before the same-commit hygiene rule could fire — the AGENT_LOG entry records this). https://claude.ai/code/session_01Xzyc27Nx3f8WC5KzwfWfjx
Two lance-graph PRs merged this evening, both touching the standalone perturbation-sim crate: #513 (merged 20:27:59 UTC, 8a3e335) — +1009/-2: - §0 promotion gate: GuardrailVerdict::RatifiedReuse for inertia_buffer (takes ResidueEdge INERTIA_SLOT=5, reuses existing tenant, no new axis → passes by reuse not waiver) - Probe 1: CAKES + CHAODA-lite over HHTL basins - Probe 2: witness arc as standing wave via Parseval (particle == wave to 0.00e0; O(N)-per-arc read-many amortization) - Probe 3: per-bus inertia (H) ingest path #512 (merged 20:33:00 UTC, 1e23c41) — +591/-5: CODE FIXES (review of #511): - calibrate.rs: divide-by-zero guard on degenerate grid (CodeRabbit Major) - basin_lambda2: assert_eq!(keys.len(), grid.n, …) precondition, promoting silent corruption to loud panic (CodeRabbit Major) - TECH_DEBT.md MD018 reflow (CodeRabbit Minor) DOCTRINE (the structural delivery, NEW to this session): - .claude/knowledge/core-first-transcode-doctrine.md (218 LOC, mandatory-read) - 3 specialist agent cards: core-first-architect, core-gap-auditor, adapter-shaper - BOOT.md + README.md wires - EPIPHANIES entry (24 LOC) - CLAUDE.md doctrine wire-up (+21 LOC, content unread by this thread) The core-first doctrine is likely directly aligned with the ontology-first stance the operator locked in on odoo-rs this session (Odoo's ontology runs natively in SurrealDB, codegen is the deferred "cut tail"). Cross-doctrine reconciliation between core-first-transcode-doctrine.md and the existing lab-vs-canonical spine not yet inspected here — flagged in PR_ARC entry confidence line. Retroactive batch hygiene — both merges landed before the same-commit rule could fire. PR_ARC prepend (newest #512 above #513 above #511) + LATEST_STATE dated bullets + recent-shipped rows. https://claude.ai/code/session_01Xzyc27Nx3f8WC5KzwfWfjx
|
Warning Review limit reached
More reviews will be available in 9 minutes and 41 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7b4cc2bf48
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| > | ||
| > **2026-06-16 — MERGED #513** (perturbation-sim: inertia §0 promotion gate + CAKES/CHAODA + witness standing-wave + H ingest): +1009/-2 across 10 files. Disjoint from #512 by design. **(1) §0 gate** — `GuardrailVerdict::RatifiedReuse`: `inertia_buffer` takes `ResidueEdge` `INERTIA_SLOT = 5`, reuses an existing tenant, invents no new axis → passes §0 by **reuse, not waiver**. Topology stays HHTL-OGAR GUID key; the buffer is one more value, orthogonal by key/value split. **(2) Probe 1 CAKES + CHAODA-lite** over HHTL basins: per-basin `[λ₂, size, inertia]` features; `CHAODA_FLAG=0.75` mirrors ndarray::clam's flag; example `chaoda` flags planted brittle block (basin 1.1.0, score 1.000). Full `ClamTree` ensemble path gated on local ndarray sibling. **(3) Probe 2 witness arc as standing wave** (METHODS §11): `particle == wave` via Parseval (`Hᵀ·H = N·I`), agreement to **0.00e0**; `witness_from_spectrum` is the O(N)-per-arc read-many amortization win. **(4) Probe 3** per-bus inertia (H) ingest path opened. Branch `claude/perturbation-sim-inertia-clam`, merge `8a3e335b`. Does NOT touch `canonical_node`. | ||
| > | ||
| > **2026-06-16 — MERGED #511** (perturbation-sim: substrate calibration + calibrated SoA member spec): **+886/-0 additive**. New `examples/calibrate.rs` (318 LOC) runs the ICC(2,1) + Spearman + Pearson + Cronbach α battery against perturbation-sim as ground truth; new `src/columns.rs` (177 LOC, spec only) names the calibrated `SoaMemberSpec` set; new `src/hhtl.rs` + `examples/hhtl_grid.rs` + `CLAM_CHAODA_FRAMING.md`. **Findings:** all 5 contingency factors certify by VALUE at 2-bit linear (ICC ≥ 0.96) — existing palette/turbovec tenants already suffice, §10 "statistics survive the encoding" CONFIRMED; α preserved within Δ ≤ 0.02 at ≥4-bit; cross-axis ρ wobbles ±0.15 at N=24 → read ≥6-bit. **Self-correction:** `d_lambda2`'s ICC=0 was variance-guard underflow at ~1e-7 magnitude (not heavy-tail / not near-constant — both prior guesses retracted); normalized storage fixes to 1.00 at 2-bit. **Locked:** 5 factors → existing tenants (no new columns for contingency axes); the **one genuinely additive member is `inertia_buffer`** — orthogonal to topology (`Spearman(λ₂, buffer) ≈ 0` per PR #509), spec only, promotion gated by §0 anti-invention guardrail. Significance per Jirak n^(p/2−1) (I-NOISE-FLOOR-JIRAK). Does NOT touch the operator-locked `canonical_node`. Branch `claude/perturbation-sim-calibrate-soa`, merge commit `c3dddfc9`. 71 lib tests + clippy + fmt clean. |
There was a problem hiding this comment.
This cold-start entry says all five contingency factors certify at 2-bit storage, but the merged #511 code it documents already uses a 4-bit robust spec for infight: crates/perturbation-sim/src/columns.rs says only four factors certify at 2-bit and defines spec("infight", 4, false). Future contract-promotion work following this board entry would allocate too narrow a tenant for infight and reintroduce the marginal 0.93–0.96 ICC case instead of the documented robust 4-bit width.
Useful? React with 👍 / 👎.
…eflight
Read-based map (full reads of every critical-path consumer + two Opus inventory
agents for the rest) produced BEFORE any wiring, per operator directive ("map
the many dependencies before"; "two paths step by step, never delete the old
before testing the new"; "CausalEdge64 is duplicated — no handwaving").
Contents:
- §0 the two stores side by side; the D-MBX-A2 gap (content/topic/angle dense
hot per OQ-1-resolved, sigma, temporal, expert); cycle (Vsa16kF32) = DROP.
- §1 the CausalEdge64 duplication mapped exactly: causal_edge::edge (SPO baton,
used everywhere) vs ndarray::hpc::causal_diff (weight-diff codec, NEVER
imported into lance-graph). Both repr(transparent)/u64 → silent-corruption
hazard at the u64 level. The contract's raw-u64 edges_raw() is the firewall;
typed reattach only at MailboxSoA owner + p64-bridge. v2 layout drops temporal.
- §2 consumer map: column hot-spots (engine_bridge + driver), the 2 bin
construction sites, the 4 Arc::get_mut single-owner hazards, the singleton-
bound tests, and the ALREADY-built cold side (surreal_container
SurrealMailboxView impls MailboxSoaView; scheduler generic over it; the
driver already holds both bindspace + mailboxes).
- §3 W0–W7 delete-last wiring sequence (parity test W1, differential test W2,
feature-gated engine_bridge/dispatch swap W3/W4, bins W5, tombstone W6,
delete BindSpace LAST W7).
- §4 dedup hazards checklist.
No source wired. Branch off main (post-#516), independent of the open #515.
Co-Authored-By: Claude <noreply@anthropic.com>
2 participants
Summary
Retroactive batch board-hygiene for four merges that landed before the same-commit hygiene rule could fire. Pure
.claude/board/*.md— no source changes, 119 insertions, 0 deletions across 3 files. Rebased onto currentmain(post-#514) so the recentTECH_DEBT.mdrelocation by #31a5cd6 is preserved (not reverted by stale content).The 3 commits are kept separate so the per-PR review surface stays scannable; could squash on merge if preferred.
Commits
4e9f755docs(board): PR test(surreal_container): additive seam falsifier — SurrealMailboxView → VersionScheduler → KanbanMove #510 board hygiene — PR_ARC prepend + LATEST_STATE rowtest(surreal_container): additive seam falsifier — SurrealMailboxView → VersionScheduler → KanbanMove #510 surreal_container seam falsifier —
SurrealMailboxView → VersionScheduler::on_version → KanbanMove(IN-direction only). Five kill-condition-first tests pin the doc-comment contract end-to-end. Deferred (explicit in test(surreal_container): additive seam falsifier — SurrealMailboxView → VersionScheduler → KanbanMove #510's body): the OUT-direction planner-emit half =D-MBX-A6-P3— still the next unblock for closing the loop.23823cadocs(board): PR perturbation-sim: substrate calibration (study as ground truth) + calibrated SoA member spec #511 board hygiene + odoo-rs seed AGENT_LOG entryperturbation-sim: substrate calibration (study as ground truth) + calibrated SoA member spec #511 perturbation-sim substrate calibration + calibrated SoA member spec. Locks: the 5 contingency factors certify by VALUE at 2-bit linear (existing tenants suffice, §10 "statistics survive the encoding" CONFIRMED);
inertia_bufferis the one genuinely additive member, spec only, promotion gated by §0. Self-correction visible: twod_lambda2ICC=0 guesses retracted on the run. Also carries the AGENT_LOG entry for the seed ofAdaWorldAPI/odoo-rs(commitebfb2c3on that repo'smain).7b4cc2bdocs(board): PR fix(perturbation-sim): degenerate-grid + key-cardinality guards (review #511) #512 + feat(perturbation-sim): inertia §0 promotion gate + CAKES/CHAODA + witness standing-wave + H ingest #513 board hygiene — retroactive batch updateinertia_buffer§0 promotion gate —GuardrailVerdict::RatifiedReuse(passes by reuse, not waiver); Probe 1 CAKES + CHAODA-lite over HHTL basins; Probe 2 witness arc as standing wave (Parseval, particle == wave to 0.00e0); Probe 3 per-bus inertia (H) ingest path. Does NOT touchcanonical_node.assert_eq!precondition, MD018) PLUS the structural delivery — newcore-first-transcode-doctrine.md(218 LOC, MANDATORY-read), 3 specialist agent cards (core-first-architect,core-gap-auditor,adapter-shaper), CLAUDE.md wire-up. Likely aligned with the ontology-first / codegen-as-cut-tail stance the operator locked onodoo-rsthis session.Why retroactive
Honest acknowledgement: the CLAUDE.md "Mandatory Board-Hygiene Rule" says updates must land in the same commit as the work; that's the discipline. Four merges blew through that window in fast succession. This PR is the cleanup commit pattern the rule itself flags as an anti-pattern — landed here as a single batch to minimise the catchup tax and so the board reads correctly for the next cold-start.
Diff stat
Test plan
origin/main(d81a139, post-docs(board): relocate CI test-job debuginfo addendum to a prepended entry (append-only hygiene, #512 review) #514) — TECH_DEBT.md update by31a5cd6is preserved, not reverted🤖 Generated with Claude Code
https://claude.ai/code/session_01Xzyc27Nx3f8WC5KzwfWfjx
Generated by Claude Code